-
Notifications
You must be signed in to change notification settings - Fork 807
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable recommended golang-ci linters #2204
Conversation
Code Coverage Diff
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Largely lgtm 👍
Left a few non-blocking comments.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: torredil The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm (other than needing a squash - please don't approve until those fixup commits are squashed)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Is this a bug fix or adding new feature?
Refactor
What is this PR about? / Why do we need it?
We rely on golang-ci's suite of linters to analyze our code for potential errors or style issues. We have had most linters disabled for a while, instead relying on PR reviewers to catch common errors.
This PR re-enables golang-ci's linters, and refactors the code base to pass those linters.
Please see .golangci.yml for a list of enabled/disabled linters and individual commit messages for the code changes required to enable each of them.
It was requested that this be a single PR, though if it takes too long to review I will split it into two PRs:
What testing is done?
Manual testing, CI, make verify